Click to view our Accessibility Statement or contact us with accessibility-related questions
Thanks for pointing this out guys, it's been fixed now.
:)