https://bugs.documentfoundation.org/show_bug.cgi?id=102043
--- Comment #4 from V Stuart Foote <[email protected]> ---
(In reply to Yousuf Philips (jay) from comment #3)
> (In reply to V Stuart Foote from comment #1)
> > Hmm, not sure this is the *right* thing to do. Seems that UI implementation
> > that does not lend itself well to supporting Assistive Technology (AT) needs
> > to be adjusted to by default support AT use--and not implement options for
> > it.
>
> Similar to how we put the most important features in the context menu to
> provide easy access to them for mouse users to speed up their workflow, a11y
> always title inserted objects, so to speed up their workflow we can
> automatically popup the dialog.
>
@Jay, think we need to rethink that--it is not to support an AT tools workflow,
but to produce documents and provide a UI that meet minimal standards for
accessibility. Our current defaults do not do that! The UI option should be the
reverse--that we produce compliant documents by default, but allow users an
optional UI to streamline their workflow but that can produce non-compliant
documents unless they add the missing annotation.
> (In reply to Jean-Philippe MENGUAL from comment #2)
> The intent is to provide a better workflow for a11y users and not to worsen
> the workflow for non-a11y users. It wouldnt be good UX for non-a11y users to
> always get prompted to name an inserted object, as they can see the object
> in their document.
Neither the project nor TDF can afford that position--were it true. It is a
question of reasonable accommodation--while individual users may elect to
produce documents not mindful of supporting accessibility requirements the vast
majority of users must prepare compliant documents. Most governmental
organizations are obliged to meet the 38 A/AA level WCAG 2.0 success
criteria--IMHO the TDF and the project are committed to meet those requirements
as they must be.
=-ref-=
WCAG 2.0--ISO/IEC 40500:2012--success criteria
https://www.w3.org/TR/wcag2ict/
and the related W3C ATAG 2.0
https://www.w3.org/TR/ATAG20/
Both the EU and US incorporate by reference the WCAG 2.0 criteria, meaning that
to meet statutory requirements LibreOffice UI must meet criteria both in its
usser interface as document "authoring tool" and in the documents it creates.
Clause 10 & 11 of EN 301 549
http://mandate376.standards.eu/standard
United States Access Board Section 508 rules
https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/proposed-rule/text-of-the-proposed-rule
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
