The manager should therefore also be accessible to the employees of a company who maintain the website.
Are there any plans to make this happen?
Here are some points I am thinking about:
I know the MODX A11y project will never be released, and now we have a completely cool new manager on MODX3.
ExtJs should be replaced on MODX4. So that is a long way to go.
There are some ideas like MMX initiative - the Mmodern MODX approach to use VueJS in the manager. This could be extended with more A11y features like ExtJS (from my point of view) but is third party.
If you read the GitHub issues from 2016/2019, there was also a discussion about moving away from ExtJS to some vanilla JS with better accessibility from @markh.
I think we can add some small tweaks like showing the current focus (remove .ext-webkit :focus { outline: none !important; } and making the main UI elements (navigation, resource buttons and tree) more keyboard and screen reader friendly without reinventing the whole manager UI.
Maybe we can crowdfund some money to pay a freelancer to optimise some major bugs (like Sterc @nomark did with the first MODX3 Version)? We also have some budget on open collective, does anyone know what happens to that money? I have some money to spend, but I am holding on to it until I know what the community want to do with it
Off topic: Writing this brings me to an old idea of having a monthly round-up. I like @bobray blog posts on the modx.com blog. And @rthrash announced more MODX marketing a few months ago, if I remember correctly. Maybe there will be a monthly blog post on modx.com reflecting on the last few weeks and looking into the future? Collecting plugin releases, MODX tips and so on. I think it happens a lot, but you have to read some sources to get the info.
Hey @jenswittmann thanks for posting this and highlighting an important shortcoming in Revo and some possible solutions. I’ve shared this with the team and the folks on the MODX Community Slack. My preference would be to have any discussion on this out in the open.
@Jens A couple of questions on the Barrierefreiheitsstärkungsgesetz (BFSG) itself (vs MODX accessibility) as I don’t trust Google Translate
Does it apply to all IT systems, or new ones created after 28 June 2025?
It recommended for all websites that are launched after 28 June 2025, provided they have a digital business transaction (form, appointment booking, shop, etc.). The backend (MODX Manager) should also be accessible to employees, regardless of the law
Is there a distinction between the customer-facing side and internal business-system side (like the MODX Manager)?
The frontend is the most important part of the site, as it is usually the one that gets the most traffic. Due to the creative freedom of MODX, this is not a problem.
The backend should also be accessible to all employees to post news or upload documents. This is an important point when pitching MODX to clients for new projects. The WP Gutenberg is accessible in mind.
It’s good to know that it applies to new websites after 28 June 2025. Does it affect updates to existing websites e.g. adding a new form?
There’s two topics in this thread, MODX Manager Accessibility, and what the BFSG requires. The second is the part I’m interested in (and why I didn’t ask on this thread), as what becomes law in Germany is likely to affect the rest of Europe.
In the UK we have regulations for public sector (often government) websites and mobile apps to be accessible, currently WCAG 2.1 AA (and soon 2.2 AA). Has BFSG adopted a recognised standard or created its own?
We have distinctions between what employers have to do under employment law/equality legislation and what’s required for services facing the general public. Does BFSG make any distinction, or is this covered elsewhere in German employment law? (I’m trying to understand exactly who the new law applies to).
Does it affect updates to existing websites e.g. adding a new form?
Yes, if you add a digital business transaction later.
Has BFSG adopted a recognised standard or created its own?
Its mostly Web Content Accessibility Guidelines (WCAG) 2.1 AA.
Does BFSG make any distinction, or is this covered elsewhere in German employment law?
Thats a good question. I’m not sure in the moment. Beside the law, everything i produce should be accessible in most cases. So I’m not 100% informed on this point, but i keep an eye on this. Thank you for keeping me up to date for the status in UK
