diff --git a/_data/authors.yml b/_data/authors.yml index 7a8e8aa769..6123b057ed 100644 --- a/_data/authors.yml +++ b/_data/authors.yml @@ -699,6 +699,10 @@ authors: name: "Peter Ling" author-summary: "I am a Senior Developer, based in Bristol. I'm interested in what technology can do for society, and what creativity can do for the soul." picture: PL_Headshot.JPG + pmarsh: + name: "Peter Marsh" + author-summary: "A keen and creative developer based in Edinburgh. Loves making music, drawing and the great outdoors" + picture: picture.jpg pshek: name: "Paulin Shek" author-summary: "

Paulin is a Java developer at Scott Logic. When she's not programming, she can be found doing cryptic crosswords and climbing small rocks.

" diff --git a/_posts/2024-05-28-a-software-developers-perspective-on-the-european-accessibility-act.html b/_posts/2024-05-28-a-software-developers-perspective-on-the-european-accessibility-act.html new file mode 100644 index 0000000000..b47e53aec8 --- /dev/null +++ b/_posts/2024-05-28-a-software-developers-perspective-on-the-european-accessibility-act.html @@ -0,0 +1,422 @@ +--- +title: A Software Developer's Perspective on the European Accessibility Act +date: 2024-05-28 09:00:00 Z +categories: + - Tech +tags: + - accessibility + - law +summary: A developer takes a dive into the lands of legislation. What is the EAA and what does it mean for me and my company? +author: pmarsh +--- + +

+ Within Scott Logic is the accessibility and ethical software working group, a + modest team eager to explore the nuanced and crucial but often overlooked + domain of software accessibility. Some time ago we caught wind of the European + Accessibility Act (EAA), a new set of rules which will be enforced from June + 2025. We quickly realised it was a rather compelling reason to get more folk + in the company interested and clued-up on accessibility. But what exactly does + the act cover, what does it mean for software companies and for Scott Logic + which builds software for other companies? What things must be done before the + looming 2025 deadline? +

+ +

+ Eager to gain a fuller understanding of the act I took a dive into the web, + taking care to dodge bias from accessibility product marketing teams, scouring + various articles and having a go at interpreting dense legal text. What + follows is my best summary of what I've found! +

+ +

+ Note: I am just a humble developer, and have had no legal training. This + article is not legal advice. I may well even get some things wrong. +

+ +

+ My research was conducted in the interest of Scott Logic, and is therefore + concerned with services rather than products (usually physical goods). If + you are interested in how the act affects products, I suggest you take a + look at a different article. If you are interested in services, then read + on… +

+ +

In Short

+ + + +

The Requirements

+ +

+ The thing about the requirements [1 - annex I] is that some of it + is up to interpretation. For example: +

+ +
+ “[make] websites, including the related online applications, and mobile + device-based services, including mobile applications, accessible in a + consistent and adequate way by making them perceivable, operable, + understandable and robust” +
+[1 - Annex I, section 3(c)] + +

+ This is written to be broadly applicable. So how am I, as a developer, meant + to apply my technical knowledge to adhere to that? +

+ +

+ Luckily for us, the act comes with a harmonised technical standard. A + technical standard is a much more focussed, technology based, + low-level set of rules to follow. WCAG, which I hope you have heard of, is + also such a standard. Harmonised means that following the standard + guarantees your service to be in line with the act. +

+ +

+ The particular standard that comes with the EAA is given the catchy name: + EN 301 549 version 4.1.1 [2]. Complying with this + standard guarantees that you are complying with the act. So, what's included + in EN 301 549 version 4.1.1? Well… We don't know. They are aiming to publish + it in 2025, which is unfortunate given that the act is to be enforced from + June 2025! However, looking at previous versions of EN 301 549, we can + anticipate that it will look extremely similar to WCAG (2.2 AA) and WCAG2ICT + which extends those rules for the web to apply more broadly to include non-web + applications [3]. +

+ +

The Scope

+ +

The act defines a list of services that it covers:

+ + + +

+ Is that all? Yes - indeed the scope is not comprehensive, but it covers many + of the crucial services that people need. +

+ +

+ When it comes to products, we cover general purpose computer hardware like + computers, smartphones and their operating systems, as well as e-readers and + many self-service terminals, like ATMs and ticket machines. +

+ +

What's Not in Scope?

+ + + +

What happens if I don't comply with the act?

+ +

+ First off, the act is an EU directive, which means that it is up to individual + member states to come up with and enforce laws. The act provides standards + that companies selling to these companies must meet, but individual companies + may choose to impose even stricter laws than the act sets out. +

+ +

+ Furthermore the individual states can choose how punishment is dealt to those + not following the laws they've put into place. The act only asserts that + penalties for non-compliance must be “effective, proportionate and dissuasive” + [1 - article 30. 2.]. +

+ +

+ So in effect the consequences of not complying depend on which country your + business sells to. +

+ +

My Takeaway

+ +

So to answer the questions I set out at the start:

+ + + +

+ I went into this research with the naive expectation that would fix all the + accessibility problems with the internet in one fell swoop. It's no wonder + that my first feeling when I concluded the research was disappointment. While + it seems there will be a large impact for products, not all crucial services + will be required to be accessible. I had also hoped that the directive would + have an impact for services used internally within companies by employees. + While that's not the case, I'm hopeful that the increased awareness of + accessibility within the tech community will have positive knock-on effects on + those areas as well. +

+ +

+ A few colleagues also pointed out the loopholes that companies might use to + evade the costs implementing accessibility. They pointed out that certain + member states could be less diligent in tracking and enforcing compliance with + the law. A cunning company could take a gamble and sell their service in one + of these more lax states, avoiding stricter enforcement while still reaping + the benefits of the EU free market. They also noted that many companies will + probably make the case for the disproportionate burden exemption and it is + still unclear how lenient or strict these will be applied is yet to be seen. +

+ +

+ My outlook brightened when a more optimistic colleague pointed out that + actually this is the first EU accessibility directive to apply standards to + public sector technologies. We've effectively gone from zero to this which is + a great step in the right direction, and all progress comes one step at a + time. +

+ +
+ "when it comes to accessibility right now, the bar is on the floor. The EAA + just picks it up." +
+ +

+ She also reasoned that legislation will influence culture around + accessibility. Now that the law is enforcing a certain standard of + accessibility, overall knowledge and awareness will increase, companies (even + those not directly affected by the act) will brag about how accessible they + are, and individuals will feel empowered to complain and take action when they + encounter inaccessible services. +

+ +

+ Historically accessibility has been viewed as an afterthought, and often a + burden. The EAA marks a shift where accessibility is a necessity and sets a + new expectation from consumers for companies providing any service. Let's hope + we keep taking steps toward an accessible web for all! +

+ +

References and Further Reading

+ +

+ Here are the sources I referenced in the article, including the official text + of the EAA. +

+ +
    +
  1. + The full original text of the act +
  2. + +
  3. + ETSI: EN 301 549 V3 the harmonized European Standard for ICT + Accessibility +
  4. + +
  5. + TPGi talk: What is the European Accessibility Act (EAA)? Countdown to EAA + 2025 (YouTube, 1hr) +
  6. +
+ +

+ I encourage you to read information from other sources too. Other posts online + will provide a different perspective! These ones I found particularly + informative: +

+ + diff --git a/pmarsh/atom.xml b/pmarsh/atom.xml new file mode 100644 index 0000000000..d866c8224f --- /dev/null +++ b/pmarsh/atom.xml @@ -0,0 +1,4 @@ +--- +author: pmarsh +layout: atom_feed +--- \ No newline at end of file diff --git a/pmarsh/feed.xml b/pmarsh/feed.xml new file mode 100644 index 0000000000..17e6954c91 --- /dev/null +++ b/pmarsh/feed.xml @@ -0,0 +1,4 @@ +--- +author: pmarsh +layout: rss_feed +--- \ No newline at end of file diff --git a/pmarsh/index.html b/pmarsh/index.html new file mode 100644 index 0000000000..55a338c338 --- /dev/null +++ b/pmarsh/index.html @@ -0,0 +1,5 @@ +--- +author: pmarsh +title: Peter Marsh +layout: default_author +--- diff --git a/pmarsh/picture.jpg b/pmarsh/picture.jpg new file mode 100644 index 0000000000..cdb6c55dd3 Binary files /dev/null and b/pmarsh/picture.jpg differ