7 of 7 WCAG Jobs in Yorkshire

strong portfolio that demonstrates clean, thoughtful, responsive UI work for web and mobile. Experience working with or contributing to design systems. Solid understanding of usability principles, accessibility best practices (WCAG), and user-centred design. Proficiency with Figma (preferred), Sketch, Adobe CC, or similar design tools. Proficiency in Photoshop to edit, retouch, and optimise images for use across web assets and More ❯

in Authentication and Security in developing web & mobile apps Experience in NextJS, Tailwind CSS, React Native, GSAP or similar animation library, CI/automated testing Server administration Knowledge of WCAG 2.1 standards and testing Perks Why work with us? We're not just about getting the job done - we're about doing it brilliantly, with purpose, and with a good More ❯

content. Define clear learning outcomes aligned with compliance or client goals. Collaborate closely with SMEs and internal teams throughout the content development process. Apply accessibility and inclusion standards (e.g., WCAG) across all content. Use learning design frameworks to ensure consistency, clarity, and engagement. Manage multiple projects to tight deadlines using tools like Trello or Jira. Contribute to innovation in learning More ❯

Non-compliance with the accessibility regulations Checkboxes are not accessible using standard voice commands such as "Click checkbox" and can only be accessed by using "Tab" commands. This fails WCAG 2.1 success criterion 1.3.1 ( Information & Relationships ). Some radio buttons are not given group titles when tabbing to them using a screen reader. This fails WCAG 2.1 success criterion 1.3.1 … Information & Relationships ). Edit combo fields with options lists can be difficult to navigate to with voice commands when the field is completed. This fails WCAG 2.1 success criterion 1.3.1 ( Information & Relationships ). The programmatic labelling of edit combo fields with options lists is not clear when using a screen reader. This fails WCAG 2.1 success criterion 1.3.1 ( Information & Relationships … accessibility We are actively engaging with our site developers and independent accessibility professionals to address the issues above and improve overall accessibility with the eventual goal of attaining full WCAG AA compliance. Preparation of this Accessibility Statement This statement was prepared on 22nd July 2021. It was last reviewed on 22nd July 2021. This website was last tested on More ❯

Start date - 7th August Location TBD (Newcastle, Leeds or Manchester) - weekly travel Inside IR35 Front end: Must be WCAG2.2 AAA compliant (accessible). Backend: Mix of microservices, lambda functions, and (Kafka) events. Some ETL and interaction with RPA. Likely to More ❯

Start date - 7th August Location TBD (Newcastle, Leeds or Manchester) - weekly travel Inside IR35 Front end: Must be WCAG2.2 AAA compliant (accessible). Backend: Mix of microservices, lambda functions, and (Kafka) events. Some ETL and interaction with RPA. Likely to More ❯

Non-compliance with the accessibility regulations Checkboxes are not accessible using standard voice commands such as "Click checkbox" and can only be accessed by using "Tab" commands. This fails WCAG 2.1 success criterion 1.3.1 ( Information & Relationships ). Some radio buttons are not given group titles when tabbing to them using a screen reader. This fails WCAG 2.1 success criterion 1.3.1 … Information & Relationships ). Edit combo fields with options lists can be difficult to navigate to with voice commands when the field is completed. This fails WCAG 2.1 success criterion 1.3.1 ( Information & Relationships ). The programmatic labelling of edit combo fields with options lists is not clear when using a screen reader. This fails WCAG 2.1 success criterion 1.3.1 ( Information & Relationships … accessibility We are actively engaging with our site developers and independent accessibility professionals to address the issues above and improve overall accessibility with the eventual goal of attaining full WCAG AA compliance. Preparation of this Accessibility Statement This statement was prepared on 22nd July 2021. It was last reviewed on 22nd July 2021. This website was last tested on More ❯