Simple language changes #490
Conversation
GeorgeKerscher
requested review from
mattgarrish,
gregoriopellegrino,
clapierre,
madeleinerothberg,
avneeshsingh and
gautierchomel
| these images; are there page numbers which are accessible; is the reading order correct so a caution | ||
| after reading a paragraph which could be dangerous will be announced? All of these, and more | ||
| accessibility concerns are potential issues consumers have when trying to purchase and ultimately read a | ||
| these images; are there page numbers which are accessible; is the reading order correct so a caution will be announced before reading the paragraph which could be dangerous? All of these accessibility concerns are potential issues consumers have when trying to purchase and ultimately read a |
There was a problem hiding this comment.
I understand the intent, but this amusingly sounds like reading paragraphs is dangerous.
Maybe the focus could be returned to the content, so phrase this as "is the reading order correct so a caution is announced before dangerous instructions".
| specific accessibility needs.</p> | ||
|
|
||
| <p>All accessibility metadata is meant to be machine-readable – except for the accessibility summary - in | ||
| <p>All accessibility metadata is meant to be machine-readable, except for the accessibility summary. in | ||
| this way accessibility metadata can be extracted and displayed uniformly across different publications |
There was a problem hiding this comment.
A summary can be read by machine, but it's not really processable in the same way as controlled terms, so I'm not sure this is the best explanation. Maybe this could be:
Most accessibility metadata uses controlled vocabularies to allow it to be extracted and displayed uniformly across different publications and localized to different user interface languages. The one exception is the accessibility summary, which allows accessibility statements that are unique to a publication.
But I wonder if we really need to get into the technicality of the summary. Maybe the last sentence could just be dropped.
This address issues 486 and 465.
@[email protected]
submitted 486, which were excellent edits in many places.
@[email protected]
Mark submitted 465, which adds libraries to the list of who should use these guidelines.
No changes were made to strings. Only the primary guidelines were changed.