v2.1.9 - Bug fixes for hiding/unhiding Twitter carousel.v2.2.0 - Bug fixes for DuckDuckGo and sizing of Export/Import.v2.2.1 - Bug fixes for Google Images and Yahoo.v2.2.2 - Bug fixes for Google "flex" layout and export/import Close button.v2.2.3 - Initial fix for updated DuckDuckGo layout.If that does not help, please use the "Feedback" tab to start a new discussion. You can find explanations of most functions on my site here. If you need to extract your block list from before Firefox 57 and move it to Tampermonkey or Violentmonkey, or to the newest Greasemonkey, please see: Questions and Problems The author is not responsible for you missing a result you might have liked to see, or other malfunction of the script. See: this recent thread.ĭisclaimer: Google search is a very complex application, so there is no guarantee that this script will work for you. (The script is partially compatible with the new Greasemonkey but it's not quite there yet.)įirefox 52 ESR/Waterfox Classic users: If you are using the legacy Greasemonkey extension (version 3.11), you need to manually edit version 2.1.5 or later.
#HIDER 2 PROBLEMS INSTALL#
Google Chrome users: Install the Tampermonkey extension for Chrome BEFORE installing this userscript.įirefox 57+ users: Install the Violentmonkey extension or the Tampermonkey extension for Firefox BEFORE installing this userscript. No typing required.įor a one-minute video overview, and a detailed description of the script, please see the following page: System Requirements Want to filter out some useless, spammy or offensive sites from Google, DuckDuckGo,, Bing and Yahoo search results? Just click "block" to reduce a site's hits to a one-line notation, or hide it completely. This can be used to hide decorative parts of a web page, such as icon fonts - that are not meant to be read by assistive technologies.Ī focusable element with aria-hidden="true" is ignored as part of the reading order, but still part of the focus order, making it’s state of visible or hidden unclear.Easily Hide Unwanted Domains in Google Results The rule applies to any element with an aria-hidden="true" attribute.īy adding aria-hidden="true" to an element, content authors ensure that assistive technologies will ignore the element. Note: Using aria-hidden="false" on content that is a descendent of an element that is hidden using aria-hidden="true" will NOT expose that content to the accessibility API and it will not be accessible to screen readers or other assistive technologies. If aria-hidden is used to hide visible content from screen readers, the identical or equivalent meaning and functionality must be exposed to assistive technologies. Aria-hidden may be used with extreme caution to hide visibly rendered content from assistive technologies only if the act of hiding this content is intended to improve the experience for users of assistive technologies by removing redundant or extraneous content. Using the aria-hidden="true" attribute on an element removes the element and ALL of its child nodes from the accessibility API making it completely inaccessible to screen readers and other assistive technologies. The following examples FAIL the aria-hidden="true" elements do not contain focusable elements rule:įocusable form field, incorrectly disabled. Īria-hidden can’t be reset once set to true on an ancestor.
Ĭontent made unfocusable through disabled. Some textĬontent made unfocusable through tabindex. The following examples PASS the aria-hidden="true" elements do not contain focusable elements rule:Ĭontent not focusable by default. Use appropriate ARIA roles, states, and properties. Fix the issue by ensuring the value inside each attribute is spelled correctly and corresponds to a valid value.
0 kommentar(er)
