StatusPage | Public Status Page for UptimeRobot | Caching library

The accessible name computation is how accessibility labels are computed.

You're using aria-label too much, and the result may be difficult to listen to or outright confusing for human visitors using assistive technologies.

The first rule of ARIA is don't use ARIA unless you really have to.

• It is appropriate to use aria-label on the

  and elements. Keep that.

• I can't think of any good reason to use aria-label on a

  element. I'd recommend removing that.

  • Using aria-label on anchor elements is normally unnecessary and should be approached with caution. Unless you have a really good reason, you probably shouldn't be presenting different content to visitors using assistive technology.

  • I would also recommend removing aria-label from your images. This is exactly what alt text is for.

  If you really want to use aria-label on anchor elements, WCAG has some guidance:

  Per the Accessible Name and Description Computation and the HTML to Platform Accessibility APIs Implementation Guide, the aria-label text will override the text supplied within the link. As such the text supplied will be used instead of the link text by AT. Due to this it is recommended to start the text used in aria-label with the text used within the link. This will allow consistent communication between users.

  https://www.w3.org/WAI/WCAG21/Techniques/aria/ARIA8.html#description

  Don't give up on NVDA just yet. I also found the default speech settings too fast and difficult to understand. You just need to adjust the settings. The voice can also be changed out for better ones. It takes a bit of work to configure, but in my opinion NVDA is the best free screen reader available today. VoiceOver is also very nice if you have access to Mac/iOS products.

In the code sample you show, you wrapped both result_name and result_ids lists into the additional lists. Rewrite the following code:

What happened sometime when you send request from a script it returns you page with different ids or class names. After driver.get('https://manage.statuspage.io/login') line save the webpage as .html file and see the id or class name there.

Turned out the problem is in rather akward design of ktor api. Summary of my findings:

Contrary to common expectation to see log events of specified log level and above it doesn't that way with CallLogging. It expects exact match of the logging level which minimizes usefulness of this feature.

You need to overwrite logger specified in ApplicationEnvironment.log. But if you follow official ktor examples and do it like this

If your intent is to parse the JSON text into (nested) objects ([pscustomobject] graphs) anyway, you can simply use Invoke-RestMethod rather than Invoke-WebRequest, because Invoke-RestMethod has ConvertFrom-Json built in, in a manner of speaking:

Should be fixed when you use {{ page.url | prepend: site.baseurl }}.

This is an issue on Content Security Policy usage on Gatsby. See more explanation on [1]. Gatsby cannot be used with a CSP rule directly.

For that there are some plugins, for example one at [2] that make it happen that CSP rule is partially generated by Gatsby. The errors get fixed.

Source:

[1] https://github.com/gatsbyjs/gatsby/issues/10890

[2] https://www.gatsbyjs.com/plugins/gatsby-plugin-csp/

You have to whitelist your origin(localhost:3000) from your Kotlin backend.

error is due to