AccName glossary

Hi,

there is a very large glossary. Having it come before the main content  
suggests to the reader that it is critical to understand all the terms -  
and for the reader familiar with them already, it just makes it more  
annoying to skip through to the content.

It would be helpful to move the glossary to follow the principal content.

Yes, there are links in the Table of Contents, but people often try to  
read documents without skipping through them.

Many terms in the glossary are not used in the document (or only used to  
define other unused terms) and should be removed:

activation behaviour
desktop focus event
graphical document
keyboard accessible
landmark
live region
managed state
nemeth braille
ontology
operable
owned element
owning elementroot wai-aria node
sub-document
taxonomy
valid idref


Some terms should be removed although they are used in the document:

Assistive technologies
This is used once in the abstract and once in the text in an informative  
note. In both cases the document *should* use "user agent".

Class
The definition given is a common one, but the term is used in many  
different ways in the document making the glossary entry actively  
misleading.
Perceivable
This is used once in the document, in its standard english sense, and does  
not need to be in the glossary.
Relationship
This is used twice in the document, in its standard english sense and does  
not need to be in the glossary.
Semantics
The definition of semantics is a standard meaning, and in addition the  
only time the term is used in the document it has a different, more  
specialised, but still common meaning.
Widget
This is used once in the document. If the term needs definition, it should  
be replaced by a word or phrase that does not need a glossary entry.

cheers

Chaals


-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Wednesday, 11 November 2015 11:00:11 UTC