FAST: Further editorial suggestions

Hi all,

Here are some other suggestions/rewrites for the FAST content.

# Rewrite - sounds odd:

"For every user interface object type, there is a clearly defined 
mechanism for authors to provide and / or user agents determines the 
"accessible name" for accessibility APIs."

To something like:

"For every user interface object type, there is a mechanism for authors 
or user agents to provide  the "accessible name" for accessibility APIs."

# Rewrite: For user interface objects that can have states, properties, 
or values, authors can set these and these can be exposed to 
accessibility APIs

To something like:

"User interface objects can have states, properties, or values set by 
authors and be exposed to accessibility APIs."

# Rewrite:

"Along with the role, many objects require information about properties, 
states, and values to be fully usable. @@ does this mean usable by a11y 
APIs?"

Many objects require information about role, properties, states, and 
values to be fully usable.

  # Provide references and definitions for things like imperative 
technologies. Confusing otherwise.

  # I don't know what novel widgets are? I think I know what you are 
getting at but the term is not in common usage - so we could use 
something like 'custom  widgets' as they are the type than usually need 
a11y stuff added after the fact.  As opposed to standard UIKit 
components etc.

# In 'Authors can title web pages' this  needs to be updated to cover 
component type development. identify component purpose etc by suitable 
semantically described components as needed.
# In the section  "Authors can identify regions of content," this should 
not be taken to emphasise 'main' regions.

Thanks

Josh
-- 
Emerging Web Technology Specialist/Accessibility (WAI/W3C)

Received on Tuesday, 30 June 2020 14:05:40 UTC