Skip to main content

Accessibility Pro Academy · Coming soon

Learn accessibility from the people who rely on it every day.

Short, hands-on courses for developers, designers and testers, taught by blind and disabled accessibility experts who use assistive technology for their own work. From experts to developers: how to turn accessibility policy into code you can ship.

  • Lived experience
  • Policy into action
  • Self-paced

Join the waitlist

Be first in when the doors open. It is free and commits you to nothing.

Helps us decide which courses to build first.

We keep your address, your answer and the time you joined, and nothing else; see clause 3.11 of the privacy policy.

Section 01 · Why an academy

Policies say what. Few people show you how.

Accessibility laws now reach most of the products developers build, yet the same few failures keep shipping: text too faint to read, images with no description, form fields with no label. Checklists name the rule. They rarely show what the failure is like for the person on the other side of the screen, or the smallest change that fixes it. That is what the Academy is for.

Home pages with detected failures

95.9%

Of the top million home pages in February 2026, with 56 errors on an average page. Low-contrast text alone was on 83.9% of them.

People with a significant disability

1.3 bn

About one person in six worldwide, according to the World Health Organization. Every one of them is someone's customer, colleague or citizen.

The European Accessibility Act

2025

Since 28 June 2025 it applies to new products and services sold in the EU, from online shops to banking apps and e-books.

Section 02 · What we believe

Three promises the Academy is built on.

  1. Taught by the people who live it

    Every course is led by an accessibility expert who uses assistive technology every day. You learn what a barrier feels like from someone who meets it, not only which rule it breaks. Nothing about us without us.

  2. Policy into action

    Each lesson starts from a requirement in the European Accessibility Act, the ADA, Section 508 or EN 301 549, maps it to the WCAG 2.2 success criteria behind it, and ends with a code change you can merge.

  3. The easiest way in, at your pace

    Short lessons you can take in a coffee break, self-paced, with hands-on labs in the browser. Follow a whole path or take the one lesson you need for the ticket in front of you.

Section 03 · How a lesson works

From a real barrier to a merged fix.

Every lesson is planned around the same four steps, so you always leave with something working, not only something understood.

  1. Step 1 of 4

    Meet the barrier

    Watch an instructor use a real component with their screen reader, magnifier or keyboard, and hear exactly where it breaks.

  2. Step 2 of 4

    Understand the rule

    The WCAG success criterion and the law that requires it, in plain language, with the reason it exists.

  3. Step 3 of 4

    Fix it yourself

    A lab with broken code. You change it, and the same engines Accessibility Pro runs check your fix.

  4. Step 4 of 4

    Prove it holds

    Test the result with NVDA, VoiceOver or TalkBack, then add a check to your pipeline so it stays fixed.

Section 04 · The first learning paths

What you will learn.

This is the plan, not a catalogue: every path below is being written now, and the list will change with what the waitlist asks for. Each course will publish its full contents before it opens.

  • Planned

    How disabled people use the web

    Screen readers, magnification, voice control, switch access, captions and cognitive needs, then WCAG 2.2 in plain language.

    Foundations

  • Planned

    Semantic HTML first

    Landmarks, headings, lists, buttons and links, and the accessible name. Headings are how most screen reader users move through a page.

    WCAG 1.3.1, 2.4.6, 4.1.2

  • Planned

    ARIA, only when it is needed

    Roles, states and properties, the ARIA Authoring Practices patterns, and why home pages that use ARIA average more errors than those that do not.

    WCAG 4.1.2

  • Planned

    Keyboard and focus

    Focus order, visible focus, focus hidden under sticky headers, dialogs, and route changes in single-page apps.

    WCAG 2.1.1, 2.4.3, 2.4.7, 2.4.11

  • Planned

    Forms and errors

    Labels, instructions and error messages, plus the WCAG 2.2 criteria on re-entering information and logging in without a puzzle.

    WCAG 3.3.1, 3.3.2, 3.3.7, 3.3.8

  • Planned

    Colour, contrast, motion and target size

    Low-contrast text is the most common failure on the web. Fix it in the design tokens, respect reduced motion, and size targets for real fingers.

    WCAG 1.4.3, 1.4.11, 2.3.3, 2.5.8

  • Planned

    Components that fight back

    Menus, tabs, comboboxes, carousels, toasts and live regions: the widgets that pass an automated check and still fail a person.

    WCAG 2.1.1, 2.2.2, 4.1.3

  • Planned

    Testing like a user

    NVDA, JAWS, VoiceOver and TalkBack for developers, what automated tools reliably catch (30 to 40% of WCAG 2.2) and how to test the rest.

    Manual and automated

  • Planned

    From policy to backlog

    Read the EAA, ADA Title II and EN 301 549 as an engineer, then write an accessibility statement, an ACR and a remediation backlog your team can finish.

    Law and standards

Section 05 · Policy into action

The clock is already running.

These are the dates product teams are working towards. The courses turn each one into the engineering work behind it.

  1. 28 June 2025

    The European Accessibility Act applies to new products and services sold in the EU.

    The EAA for developers

  2. September 2026

    EN 301 549 V4.1.1 is published, bringing WCAG 2.2 into the European standard. It becomes the legal reference once cited in the Official Journal.

    EN 301 549, V3.2.1 and V4.1.1

  3. 26 April 2027

    ADA Title II: state and local governments serving 50,000 people or more must meet WCAG 2.1 Level AA.

    The ADA and websites

  4. 26 April 2028

    ADA Title II: smaller governments and special districts must meet the same standard.

    The ADA Title II dates

Section 06 · Who it is for

For everyone who ships the product.

  • Developers

    Front-end, full-stack and mobile engineers who want the fix, the reason and the test, in the framework they already use.

  • Designers

    Decisions on colour, focus, motion and layout that make accessible code possible before a line is written.

  • Testers and QA

    Screen reader and keyboard testing you can repeat, and automated checks that fail the build for the right reasons.

  • Product and compliance leads

    What the law asks of your product, in the words your engineers use, and how to turn an audit into work that ships.

Section 07 · Instructors

Meet the first instructors.

The two people who build and test Accessibility Pro. Both use a screen reader every day.

Elena Karamanska, head and shoulders, with a dark brown bob and fringe, in a cream blouse against a deep red backdrop, smiling slightly.

Elena Karamanska

Accessibility specialist

An IAAP CPACC-certified accessibility consultant and screen reader user for more than twenty years, who tests websites and mobile apps with assistive technology and has reviewed more than a thousand websites for accessibility.

More about Elena

Hasan Tayem smiling at his graduation, in a black gown with orange trim, a mortarboard and a red tie, holding an orange folder beside the flag of Jordan, in front of shelves of leather-bound books.

Hasan Tayem

Founder

A totally blind digital accessibility specialist, disability rights activist and professional long-distance runner, originally from Jordan and based in Padova, Italy, who uses the NVDA screen reader for all of his digital work.

More about Hasan

Teach with us

Do you rely on assistive technology and know it inside out? We are looking for instructors who are Deaf or hard of hearing, have low vision, or have motor or cognitive disabilities, and for people who work with voice control, switch access or magnification every day.

Write to us about teaching

Section 08 · Questions

Asked before the doors open.

When does the Academy open?

We have not set a date, and we will not announce one until the first courses are recorded and tested. People on the waitlist hear first.

What will it cost?

Prices will be published before the Academy opens. Joining the waitlist is free and commits you to nothing.

Will I get a certificate?

Courses are planned to end with a certificate of completion. It shows what you learned. It is not a compliance certificate for your product, and no course replaces testing with disabled people.

Will the Academy itself be accessible?

It has to be. Every video is planned with captions and a transcript, every lab has to work with a keyboard and a screen reader, and the instructors test the platform with their own assistive technology before it opens.

Do I need to know WCAG already?

No. The first path starts from how disabled people use the web. If you already know WCAG, go straight to the path you need.

Can my team learn together?

We would like to hear from teams now. Write to support@accessibilitypro.app with the size of your team and what you need to learn; it decides which courses we build first.

Accessibility is not a feature you add. It is a skill you learn.

Learn it from the people it is for. Join the waitlist and be in the first cohort.