Accessibility Statement
This website (sparklane.dev) is frequently updated and is consistently built with care and intention. The web should be a friendly and accessible place for everyone. I aim to develop inclusively, aiming to provide good usability across a range of abilities, devices, and situations.
My accessibility standards
I aim to meet WCAG 2.2 to Level AA standard as a minimum throughout the site.
Core practices
Level AA
- semantic HTML5 with clear heading structure
- skip link to main content
- responsive, zoom-friendly layout (up to 200%)
- keyboard-accessible navigation and links
- custom focus styles for visibility
- alt text for meaningful images, decorative images hidden
- readable font sizes and color contrast of at least 4.5:1
- support for prefers-reduced-motion
Level AAA
- most body text meets or exceeds 7:1 contrast
- focus styles are consistent across browsers and high contrast
Your experience, your way
You should be able to:
- use your browser defaults for settings, sizes and styling
- zoom in (or out) without breaking your experience
- navigate the site with just your keyboard
- listen to the site using a screen reader
- choose between three color themes (green, pink, or peach) with dark and light variants while maintaining accessibility
I also make the website text as simple as possible to understand. AbilityNet has advice on making your device easier to use if you have a disability.
How accessible this website is
Parts of this website are not fully accessible. For example:
- some pages may not be written in plain English
- some images may not have adequate image descriptions
- some heading elements may not be consistent
Feedback and contact information
If you need information in a different format, please contact me:
- Email: emma@sparklane.dev
- LinkedIn: Connect with me on LinkedIn
In your message, include:
- the web address (URL) of the content
- your email address and name
- the format you need - for example, plain text, large print or audio
Reporting accessibility problems with this website
If you find any problems that are not listed on this page or you think I'm not meeting accessibility requirements, contact me.
Technical information about this website's accessibility
I am committed to making this website accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Date
This statement was created on 15 February 2026.