Add EAA blog post #2581
Add EAA blog post #2581
Conversation
zeppelin
commented
Dec 9, 2024
•
zeppelin
commented
- Find a better title than "European Accessibility Act"
- Add og-image
- Update publish date
|
Hi @zeppelin here's my recommendation. I am not sure where you want me to put it, but maybe you can review it here first: Intro TLDR Mainmatter can simplify this process for you. With our expertise and tools, we’ll help ensure your products are fully accessible, minimizing legal risks and improving the experience for all your users. Bottom line |
marcoow
force-pushed
the
zeppelin/blog-a11y-eaa
branch
from
aeea9e8 to
37a10af
Compare
zeppelin
force-pushed
the
zeppelin/blog-a11y-eaa
branch
from
37a10af to
180bc8c
Compare
|
@IdeliaRisella Thank you 🙏 I'll check with @KevinBongart first before publishing. @umbrellarocket The blog post needs an og-image, which I substituted with a blank gif for the moment 😅 Could you please help me adding one? |
|
@zeppelin I've added the og-image for now. If you do end up changing the date of publication, could you please adjust the folder name for the og-image as well (it's date dependent)? |
zeppelin
force-pushed
the
zeppelin/blog-a11y-eaa
branch
from
c653ccc to
dc0dbd1
Compare
Thank you, Xenia! Yes, I did that :) |
| Without going into details, here are some screen readers available across different operating systems: | ||
|
|
||
| - [NVDA](https://www.nvaccess.org/download/): A third-party screen reader available for Windows. | ||
| - [JAWS](https://www.freedomscientific.com/products/software/jaws/): A commercial screen reader for Windows. | ||
| - **VoiceOver**: A built-in screen reader included with macOS. | ||
| - [Orca](https://orca.gnome.org/): A screen reader for Linux systems, specifically those running the GNOME desktop environment. |
There was a problem hiding this comment.
What is the point of this section? It's just listing screen readers, not showing how Mainmatter can help with accessibility. For instance, it should suggest a screen reader simulator (e.g. https://silktide.com/toolbar/screen-reader-simulator/) for the reader to easily experience their product through such a device. The section should then explain that making web apps work with screen readers take some engineering effort both for identifying gaps and for implementing solutions which depend on the product and the tech stack, and Mainmatter can help with that
There was a problem hiding this comment.
Nobody that we spoke to or any forums recommends any kind of "simulators" . If they need to they have separate computers or VMs with windows/mac.
Silkitde's "screen simulator" doesn't help here anyway, because it doesn't show a rover (dropdown link selects) or is reading the screen (which is the most important part). It's functionality overlaps with tools recommended in previous sections such asaccessibilityinsights.
I think that it is helpful to list available screen readers, because I personally had no idea where to get them from and if all systems have it. Turns out all systems have their own solutions.
Having an actual screen reader is needed because it's the only way to test your website in "production".
Different screen readers handle aria-labels differently too.
| ## Quick intro to WCAG 2.2 (Levels A and AA) Success Criteria | ||
|
|
||
| The WCAG 2.2 guidelines establish accessibility standards based on four key principles: **Perceivable**, **Operable**, **Understandable**, and **Robust**. These principles ensure content is accessible to all users, including those with disabilities. |
There was a problem hiding this comment.
This section comes out of nowhere, with no clear connection with the EAA. I think the EAA is a superset of WCAG, so the bog post should say that and then talk about WCAG. Alternatively, the blog post should have a transition like "Let's look at some specific accessibility criteria from WCAG, which the EAA uses as a technical basis:"
There was a problem hiding this comment.
I've added the below between the section title and the WCAG 2.2 paragraph
Let's look at some specific accessibility criteria from WCAG, which the EAA uses as a technical basis.
|
|
||
| ## Bottom line | ||
|
|
||
| The European Accessibility Act is setting the bar for accessibility across the EU, with the June 2025 deadline coming up fast. It might seem like a lot to take on, but with the right tools and a little planning, it’s completely doable. Making accessibility a priority now doesn’t just help you avoid penalties—it makes your products better for everyone. So why wait? Let’s get started and make sure your digital experiences are accessible to all. |
There was a problem hiding this comment.
"with the right tools and a little planning" completely dismisses the pitch from Mainmatter that it takes experience in building web apps to identify accessibility compliance gaps and requires web engineering expertise to implement compliant solutions. This should be rewritten to highlight that Mainmatter has that experience and expertise and we have a contact form to get started with an accessibility audit
There was a problem hiding this comment.
@KevinBongart Ive replaced this with
The European Accessibility Act is setting the bar for accessibility across the EU, with the June 2025 deadline fast approaching. Achieving compliance isn't just a box to check - it's about creating digital experiences that are accessible to all. But identifying compliance gaps and implementing solutions takes more than just the right tools—it requires experience in building web applications and expertise in web engineering. With years of experience in accessibility and web development, we specialize in identifying and addressing accessibility challenges to ensure your digital products meet the highest standards.
Co-authored-by: Kevin Bongart <[email protected]>
zeppelin
force-pushed
the
zeppelin/blog-a11y-eaa
branch
from
c939030 to
079f1d6
Compare
Co-authored-by: Kevin Bongart <[email protected]>
|
Thanks for addressing my feedback @zeppelin. As for the blog post title… something straight to the point, like "Complying with the European Accessibility Act requires web engineering expertise" or something catchier? Here are 10 bad ideas from ChatGPT:
I don't think we should say "Our Senior Engineers" but the gist remains correct IMO |
There was a problem hiding this comment.
I think this is a good start but I'd have 2 suggestions:
- Let's make this sound natural and to-the-point. Some sections sound like they are either copied from the EU website or written by Chat-GPT. Those use 100 super long sentences to say the same thing we could express with 1-2 short and concise sentences. Longer sentences and more complicated wording doesn't mean things are more professional :)
- If we can, I think it would be great to make this more concrete – what specifically do I need to do to ensure compliance? What do I use the tools for specifically? Instead of starting with the theory like WACG etc., start with practical suggestions and explain the theoretical foundation for those in a 2nd step
| > TL;DR: By June 28, 2025, all digital products and services targeting EU users must meet accessibility standards under the [European Accessibility Act (EAA)](https://employment-social-affairs.ec.europa.eu/policies-and-activities/social-protection-social-inclusion/persons-disabilities/union-equality-strategy-rights-persons-disabilities-2021-2030/european-accessibility-act_en). This includes everything from websites and apps to platforms in sectors like e-commerce, finance, and education. Failing to comply could result in fines of €5,000 to €20,000 per violation, with daily penalties up to €1,000 if issues persist. | ||
| > | ||
| > Mainmatter can simplify this process for you. With our expertise, we’ll help ensure your products meet modern accessibility expectations, minimizing legal risks and improving the experience for all your users. |
There was a problem hiding this comment.
This doesn't actually seem to be a quote?
| > | ||
| > Mainmatter can simplify this process for you. With our expertise, we’ll help ensure your products meet modern accessibility expectations, minimizing legal risks and improving the experience for all your users. | ||
|
|
||
| ## Introduction to the **European Accessibility Act** |
There was a problem hiding this comment.
I'd suggest a more concise and to-the-point writing style – not just here but in general:
| ## Introduction to the **European Accessibility Act** | |
| ## What is the **European Accessibility Act**? |
| The **[European Accessibility Act (EAA)](https://employment-social-affairs.ec.europa.eu/policies-and-activities/social-protection-social-inclusion/persons-disabilities/union-equality-strategy-rights-persons-disabilities-2021-2030/european-accessibility-act_en)** is a directive designed to ensure digital accessibility across the European Union, covering websites, mobile applications, software, and other digital and physical products used in sectors like e-commerce, finance, education, and transportation. By establishing unified accessibility standards, the EAA simplifies compliance for businesses operating in multiple regions, eliminating the need to navigate varying national regulations. This harmonization reduces compliance costs, expands market opportunities, and enhances digital experiences for people with disabilities and elderly individuals. | ||
|
|
||
| Non-compliance with the EAA can lead to significant consequences, including fines and potential lawsuits. Businesses risk legal action, especially if their products or services are essential yet inaccessible. To mitigate these risks, organizations should prioritize accessibility by conducting regular audits, maintaining thorough reporting, and creating a knowledge base for customer support. By integrating accessibility into their strategy, businesses not only reduce liabilities but also foster a more inclusive user experience. |
There was a problem hiding this comment.
No offense to anyone but this sounds like it's either copy-pasted from the EU website or completely written by Chat-GPT – I assume we can say all of this with 2-3 to-the-point sentences as well?
|
|
||
| ### Compliance Timeline | ||
|
|
||
| Product owners need to be aware of these key deadlines: |
There was a problem hiding this comment.
| Product owners need to be aware of these key deadlines: | |
| Product teams need to be aware of these key deadlines: |
I'd avoid Scrum jargon in general .)
| Product owners need to be aware of these key deadlines: | ||
|
|
||
| - **June 28, 2025**: Deadline for most digital platforms (websites, mobile apps) and other covered products to comply with EAA accessibility standards. | ||
| - **June 28, 2030**: Extended compliance deadline for certain self-service terminals, such as ATMs and ticket machines. |
There was a problem hiding this comment.
Is this indeed something that teams need to prioritize now?
| ### Expansion Beyond Web Accessibility | ||
|
|
||
| The EAA builds on the Web Accessibility Directive, which originally focused on public sector websites and mobile applications, and extends accessibility requirements to the private sector. This expansion ensures that a broader range of digital and physical products in the private sector adhere to inclusive standards. The EAA’s implementation also benefits from the models and expert groups developed for the Web Accessibility Directive, promoting consistency in enforcement across the EU. |
There was a problem hiding this comment.
I'm not sure what this adds to the post tbh…
|
|
||
| ## Meeting compliance requirements | ||
|
|
||
| Making sure your business is compliant could be a significant amount of product design and engineering work that also requires a know-how of the web application development field. This section will provide you steps to navigate the problem. |
There was a problem hiding this comment.
| Making sure your business is compliant could be a significant amount of product design and engineering work that also requires a know-how of the web application development field. This section will provide you steps to navigate the problem. | |
| Ensuring compliance with the EAA requires product design and engineering work. This section shows the key steps. |
sounds much more natural?
|
|
||
| The cost of ensuring compliance with the European Accessibility Act depends on the complexity of your web application. The process typically begins with an initial accessibility audit to identify areas requiring updates. Simpler applications may only require one-time investments to implement these updates, while more complex platforms may involve ongoing expenses for development, user testing, and the integration of assistive technologies. Training your team is another important factor, with costs associated with workshops or courses. Additionally, businesses should consider the long-term expenses of ongoing compliance monitoring and enhancing customer support for accessibility. Failing to comply may result in fines ranging from €5,000 to €20,000 _per violation_, with ongoing non-compliance penalties reaching as high as €1,000 per day. While these efforts require investment, the benefits include broader user engagement, reduced legal risks, and a strengthened reputation for inclusivity. | ||
|
|
||
| ## Quick intro to WCAG 2.2 (Levels A and AA) Success Criteria |
There was a problem hiding this comment.
Can this be moved to the top to explain what specifically the EAA is about? Until this point I was wondering what specifically a web app needs to do to be compliant and it seemed like that might not be covered in the post since it was already talking about tools…
