GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |||||||||||
GeezerVison is showing github.com — Fix Accessibility Violations in Partner Logos Section by huangkevin-apr · Pull Request #668 · processing/processing-website ConversationProblemThe IBM Equal Access Accessibility Checker detected two accessibility violations in the partner logos section of homepage:
SolutionThis patch addresses both violations by:
Generated Patch: @@ -282,14 +282,15 @@ const IndexPage = ({ data }) => { className={css.logo} href={url} target="_blank" - rel="noreferrer"> + rel="noreferrer" + aria-label={name}> {typeof Logo === 'string' ? ( <GatsbyImage image={data[Logo].childImageSharp.gatsbyImageData} alt={name} /> ) : ( - <Logo /> + <Logo aria-hidden="true" /> )} </a> The patch submitted in this PR was generated by A11YRepair, an automated Web Accessibility repair tool that I developed to address common accessibility violations in web applications. The generated fixes were manually reviewed and validated before submission. Testing✅ IBM Equal Access Accessibility Checker now shows 0 violations (previously 2) ImpactThis fix improves accessibility for users relying on assistive technologies, ensuring all partner links are properly labeled and announced by screen readers.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
|
There was an error while loading. Please reload this page.
✅ Deploy Preview for java-processing-faf822 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Sorry, something went wrong.
There was an error while loading. Please reload this page.
There was an error while loading. Please reload this page.
Successfully merging this pull request may close these issues.
There was an error while loading. Please reload this page.