All,

I'm in the process of auditing the wicket core and extensions
components and provided functionality for accessibility issues and boy
has my agent uncovered a lot.

You can read the audit here:
https://github.com/apache/wicket/issues/1838#issuecomment-6705995932

I intend to start fixing these issues, but those have implications for
all wicket application developers: if you want to have your
application be accessible to everyone, you have to generate proper
markup that is accessible and passes the accessibility tests.

One example is adding lang and dir attributes to the <html> tags. I
have a PR ready: https://github.com/apache/wicket/pull/1870

Another example: links that are attached to <span> or other markup
tags are old relics from 2014, and we should have better ways to style
links and rows in tables, which makes them usable by keyboard and
screen readers. (no PR yet)

I'm also adding guides and references to the documentation about
accessibility and Wicket. You can see the PR here:
https://github.com/apache/wicket/pull/1847

But I don't want to go on a crusade without consulting the grander
community and keeping you in the dark until a release comes and your
applications would break. So I welcome discussion on how we can make
Wicket conform to the WCAG 2.2 from the core, and also give a clean
path forward for you to migrate your applications without migraines.

Please read the report and provide feedback, it is very much
appreciated to get all opinions on this matter.

Kind regards and on to a more accessible future for Wicket.

Martijn

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to