You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The second draft of the display guide adds to the Navigation section the example "Contains book elements such as headings, tables, etc for structured navigation"
Which is specialised wording that is hard to understand for anyone outside of technical experts.
If we are to keep this information, it could be made more understandable like "This ebook includes structure elements for headings and tables to help you navigate easily".
But I also think that this is mainly useful for AT users, so we could explicitly mention it with something like "This ebook includes structure elements for headings and tables to help assistive technologies users navigate easily."
(I resist the temptation to propose the reintroduction of "screen reader friendly")
The text was updated successfully, but these errors were encountered:
Is there common phrasing for the functionality that AT users already understand? It sounds like we're trying to explain the functionality rather name it.
I'm wondering if there's some phrasing like "ebook markup facilitates navigation by assistive technology shortcut keys" that would be more easily understandable to users.
The second draft of the display guide adds to the Navigation section the example
"Contains book elements such as headings, tables, etc for structured navigation"
Which is specialised wording that is hard to understand for anyone outside of technical experts.
If we are to keep this information, it could be made more understandable like "This ebook includes structure elements for headings and tables to help you navigate easily".
But I also think that this is mainly useful for AT users, so we could explicitly mention it with something like "This ebook includes structure elements for headings and tables to help assistive technologies users navigate easily."
(I resist the temptation to propose the reintroduction of "screen reader friendly")
The text was updated successfully, but these errors were encountered: