- computers and operating systems
- ATMs, ticketing and check-in machines
- smartphones
- TV equipment related to digital television services
- telephony services and related equipment
- access to audio-visual media services such as television broadcast and related consumer equipment
- services related to air, bus, rail and waterborne passenger transport
- banking services
- e-books
- e-commerce
For my part, I would dream of this regulation mandating backward support for browsers at least seven years back to stop the nowadays framework madness. As a great example, my bank login page is 10MB.
[1] https://commission.europa.eu/strategy-and-policy/policies/ju...
Current banks login pages are a bit below 3 MB.
I see it as a prioritization issue. Are you happy with your bank services except the size of the (login) pages? Probably they focus on what they should as there would be more customers switching due to bad service than to page sizes. There are probably few scenarios where 10 MB is a problem - most of it should get cached anyhow after the first load.
Just yesterday I stumbled upon a developer video from Germany who was trying to build some AI RAG SaaS for small businesses and was completely overwhelmed with the EU Privacy and data protection regulations and was stuttering when was talking about going to jail for using OpenAI API the wrong way.
Just Wow. These things are not for you, nobody is going to jail for their app or paying life ruining fines in Europe as long as they don't actually cause real harm. All those rules and regulations are intended for large companies who abuse their power or harm large parts of the society by ignoring stuff when not making them profit.
Edit: I'm not complaining about the regulations in this comment, I'm saying that it's bad advice to ignore them just because you're a small business unless there is an exception for them. As it happens, exceptions for small business are planned.
I should be able to navigate a webpage completely by speech. The actual speech UI would take some thinking. You want both absolute by name and relative references, as in "follow that link," "third link back," "follow threads", and " follow new," as a bare minimum.
I'm very interested in how they've implemented Google Analytics. No external JS is loaded, just 9KB of packed JS embedded implementing a minimal call... and then it is being sent to their own script analytics4.php which acts like MITM. Does anyone know the name of the plugin or package they are using?
But for smaller companies, getting the website/app up to the rules for European Accessibility act can be over their limits, cause it's not an easy task, depending on the type of UI your app is using.
So their only option is just to avoid Europen market, if they don't want to go to jail.
And European Software marked will be left behind even more.
Europe has 0 power in online world and they keep it like that by making dumb rules everyday.
If this leads to better accessibility in the common frameworks or the emergence of more accessible frameworks, it will be a win for every Internet user in the world, though. This is a technical issue that can be fixed.
The purpose of this Directive is to contribute to the proper functioning of the internal market by approximating laws, regulations and administrative provisions of the Member States as regards accessibility requirements for certain products and services by, in particular, eliminating and preventing barriers to the free movement of certain accessible products and services arising from divergent accessibility requirements in the Member States. This would increase the availability of accessible products and services in the internal market and improve the accessibility of relevant information.
Due to the differences in national accessibility requirements, individual professionals, SMEs and microenterprises in particular are discouraged from entering into business ventures outside their own domestic markets. The national, or even regional or local, accessibility requirements that Member States have put in place currently differ as regards both coverage and level of detail. Those differences negatively affect competitiveness and growth, due to the additional costs incurred in the development and marketing of accessible products and services for each national market.
The approximation of national measures at Union level is therefore necessary for the proper functioning of the internal market in order to put an end to fragmentation in the market of accessible products and services, to create economies of scale, to facilitate cross-border trade and mobility, as well as to help economic operators to concentrate resources on innovation instead of using those resources to cover expenses arising from fragmented legislation across the Union.
I was once talking with the cto of an Ai law startup who made a presentation in university, and he noted that one of the main issue to move to other countries would have been different laws. Of course for the whole law sector that's impossible to harmonize (at least for the time being), but if for some things there can be harmonization, it's a win win for everything
I think this is reasonable. What you are writing feels less reasonable.
Also we can follow China's leadership and get our own digital wall.
The annoying cookie banners prove you wrong.
* Banks
* Webshops
* Operating Systems
* Software designed for Communication
The rest is all hardware devices (ATMs n such), public government services (the public transport schedule), relates to TV or isn't software in the first place (ebooks).
Banks and OSes are markets with only a few players and none of them are small. It'll be interesting to see if this on a technical level will demand changes for Wayland, afaik it's story on accessibility is pretty shit still.
Webshops overwhelmingly either use larger third parties as intermediaries (ie. Etsy) or stuff like woocommerce, an off the shelf solution developed by Automattic (who will obviously have to accommodate by updating woocommerce, which they probably will since iirc they offer a commercial solution for woocommerce themselves).
And communication software really is the big one, but most people aren't making new ones of those either. That's gonna be a pain for Slack/Salesforce, Meta, Reddit and so on, but they'll have legal pressure to comply (which opens up a lot more room to accelerate and give money to that sort of thing). If you start out in this market in particular, it'll probably be easy to comply with this regulation "from the ground up", just like how it's pretty easy to not build a data slurper from scratch after the GDPR got passed into law.
The thing they all have in common is that there's relatively few actual competing products.
In Denmark we had a year to make government/public apps fully accessible and the same for websites and documents presented on websites.
We also had to create accessibility certificates and dedicated pages on the websites to prove and clarify the state of the accessibility (or lack of, together with a statement of what's being done to remedy the issues).
Are these "new" EU laws for a different sector (private?) or something else? I can't find any references in the article. I may be blind (pun intended).
And yes, these new laws seems to be aimed for private sector as well.
That seems extremely excessive. A prime example of regulatory overreach.
The reality is that if you're ignoring this stuff, you are effectively eliminating a significant chunk of the population from participating in public life. It's about as bad as not having wheelchair ramps in public places, except the same software runs everywhere, so it's not the one virtual 'building' missing it, but all buildings made by the same architect.
In the EU the directives define a max range. Eg. 10% of global revenue or 20 million EUR whichever is higher.
Then the court figures out to what extend the company broke the law.
This system is needed to make sure that there are not some member states that are more forgiving and provides a competitive edge for companies to move there.
The better option is for the ai to review the code during development and suggest suitable accessibility measures compared to the spec and common guidelines.
It's a bit odd you could get sent to prison if your website can't be used by e.g. a blind person, but it's perfectly fine if it can't be used by someone without disabilities.