My goal with my website is to make it as accessible as possible. This page outlines the accessiblity tools and initiatives I have taken, and any limitations my website has.

While I use WCAG as a resource to inform my decisions, I am not implying I meet the standards of AAA in every mark, my goal is to come as close as I can... with my weird little avant-garde little website. But it is entirely possible to have accessability even with complexity! And to make it a little easier on the user, I try to use as little Javascript as I can and use pure CSS design, but I am willing to try to impliment Javascript approaches if nessecary (like I have with Gifa11y).

Current accessability tools and initiatives avalible on my website:

• Any page that includes GIFs has the ability to pause and unpause them in a spacebar press (does require javascript to be enabled, as we use Gifa11y here).
• Resize text up to 200% without context loss on majority, if not all, current webpages - tested on multiple screen types
• Frequent screen reader testing (NVDA)
• ARIA may be used to provide additonial context to elements, but nothing that changes the user experience fundementally.
• Non-decorative image descriptions; either below images in written articles, provided in alt text or ARIA label, or additionial visible way that is able to be read by a screenreader on mouse hover.
• Website can be fully accessable with only a keyboard. Keyboard focus indicator is visible when possible, but the element selected is never hidden.
No auto-playing audio.
• Avoiding flashing colors and eyestrain, with conditions such as photosensitivty and eplilepsy in mind - if they are present, there will be warnings.
• Multiple ways to locate public content on the website (and "easter eggs" will be available on a sitemap as well).
• Mobile versions of each page, even if they're a little scuffed, they will at least be functionial.*
• In event of contrast failure due to creative choice, stylistic borders are implimented to break the background up from the foreground - the text contrast is my biggest priority in terms of achieving the guidelines.
• Articles and text-heavy pages are made with "reader mode" in mind, can be resized up to 200%.
• Proper syntax is used in sentences and is just modified using CSS elements. This is just a personal thing I find helpful.

• Polishing the mobile website's look.
• Art image descriptions.
• Appropriate ARIA and landmark roles.
• Dark theme. May learn how to utalize cookies to make your preference remembered.
• The purpose of each link can be determined from the link text alone.

• Not sure yet, because I find this easy and fun to impliment (when these features cooperate, anyway...)

• NVDA with near out-of-box functionality
• I have an odd screenwidth and default zoom. I occasionally work at 1231 x 735 at 250% zoom (surface pro moment). I often test final versions before I submit them to the website host, at the standard HD resoluton (1920 x 1080 at 100% zoom)
• I test up to 200% zoom, but if I can't make it work at that moment, I often move on and push the update out anyway.
• For mobile layouts, I usually use firefox's web developer tools in-browser. I will sometimes test on my own phone to work out the kinks. Since phones and browsers have SO much variety, I can't promise it will look the same for me on my devices as it does yours.

If you feel I'm missing an important accomdative strategy, please contact me - I really love learning to impliment them in my website!

Please remember, this website is a hobby for me. I do not earn profit from this website directly, other than in the form of user donations (which at the time of wrtiting this, I doubt I'll get). While I wish to add as much accomidation as I can, it may not be in my scope to add certain features.

You can add me on my Discord, which is @aversart. Posting on my neocities wall is also appropriate, but you may not be able to properly describe your problem there. Any additionial contact methods through my social media pages are also fine!