I chose to handcraft this website using basic semantic HTML and CSS with the intent of being boring but inclusive before magical and inaccessible.
Why? I want everyone to have an equitable experience in judging my design talent, reading my thoughts, and contacting me because:
- inclusion makes everything better and
- it’s a civil right
anchor Conformance Status
The Web Content Accessibility Guidelines (WCAG) defines requirements for designers and developers to improve accessibility for people with disabilities. It defines three levels of conformance: Level A, Level AA, and Level AAA.
My portfolio is partially conformant with WCAG 2.1 level AA. Partially conformant means that some parts of my portfolio do not fully conform to the accessibility standard including:
- Archived pages from my old portfolio (I should delete these before they embarrass me further)
- PDFs from past presentations on my articles and talks page (I’m planning on working on transitioning these into plain old HTML when I find the time)
- Decorative font on the left and right margins that read in latin “Nihil de nobis, sine nobis” and “A11y = Accessibility” (intended to specifically target sighted folk with 20/20 vision, but does not relevantly contribute to any content)
- Semantic HTML landmarks and elements
- Logical heading structures
- Links with target and purpose
- Alternative text for images (including all of my curated memes)
- Responsive design which works on any screen size
- Large type that respects zooming and font resizing
- Reduced motion preferences are respected by default
- Finding an accessible alternative to calendly for convenient scheduling
- Noting external links
- Dark mode
anchor Testing Approach
I self-evaluated all unarchived pages in my portfolio using:
- Accessibility testing tools (axe and Wave) to catch up to 30% of errors
- Keyboard testing
- Manual screen reader testing with VoiceOver on Safari
I’m planning to include more manual screen reader testing on:
- TalkBack (Android)
- VoiceOver (iOS)
- NVDA on Chrome
- JAWs on Internet Explorer
anchor Feedback (help me do better)
I am confident that I am nowhere near 100% in terms of accessibility compliance (or my goal for accessibility beyond compliance) and am committed to doing better.
If you experience any issues on this website, please email me feedback at firstname.lastname@example.org.
anchor Some more thoughts
If I used a portfolio builder like WIX and Squarespace, I would have chosen to further the digital disability divide which wouldn’t have been very cash money.
Instead, before releasing this version of my portfolio, I dedicated a year to:
- Understanding web standards (shoutout to the blue beanie book)
- Studying inclusive design patterns and components (god bless Heydon Pickering)
- Reading every blog post written by Scott O'Hara, Marci Sutton, Adrian Roselli, Sarah Higley, and more (shoutout to David Kennedy for his a11y weekly newsletter that helped me get started)