Some more notes

_rules/target-size-enhanced-gi8qkf.md

@@ -26,14 +26,14 @@ acknowledgments:
 This rule applies ta any [HTML element][namespaced element] for which all the following are true:
 
 - the element is an [inheriting semantic][] `widget`; and
-> comment: role may be incorrectly set.
+  > comment: role may be incorrectly set.
 - the element [can be targeted by a pointer event][].
-  
+
 Exception: not for `area` (due to weird shapes).
 Exception: not if a descendant is focusable (hard to define the clickable area).
 Exception: the target is a [UI controlled component][].
-> comment: This is for the "User Agent Control" exception. The Understanding doc mentions days in a calendar widget. I somewhat intend to have this as a list of elements (or their descendants) which are known to correspond (e.g. `<input type="date">`) as it is fairly flexible and easy to define. This would, however let out cases where these components are re-sized by the author. But this is only false negatives, so I guess it's OK.
 
+> comment: This is for the "User Agent Control" exception. The Understanding doc mentions days in a calendar widget. I somewhat intend to have this as a list of elements (or their descendants) which are known to correspond (e.g. `<input type="date">`) as it is fairly flexible and easy to define. This would, however let out cases where these components are re-sized by the author. But this is only false negatives, so I guess it's OK.
 
 ## Expectation
 
@@ -42,10 +42,10 @@ For each test target, at least one of the following is true:
 - the target element has a [clickable area][] width and height of at least 44 CSS pixels; or
 - the target is part of [inline text][]; or
   > comment: I feel this is going to be difficult to define objectively, so it is better in Expectation for now. #1010 has some work in that direction that we can probably reuse: https://github.com/act-rules/act-rules.github.io/pull/1010/files#diff-32079a0602a5a909b242b4e0961e7c5ddd6b6f5c9906b216d5bf21cf2ba13a77R28-R29
-  https://github.com/act-rules/act-rules.github.io/blob/4b64bba6cb77a8d4dc0649c83c55372f513d979f/pages/glossary/rendered-on-a-line.md
+  > https://github.com/act-rules/act-rules.github.io/blob/4b64bba6cb77a8d4dc0649c83c55372f513d979f/pages/glossary/rendered-on-a-line.md
 - The size is [essential target size][]
   > comment: this is always a bit tricky. I guess we can do as in #1916 and list cases that are considered essential (list can grow).
-- There is an [instrument][] to achieve an equivalent goal, with a 44*44px [clickable area][].
+- There is an [instrument][] to achieve an equivalent goal, with a 44\*44px [clickable area][].
   > comment: I think we can go in line of "there is no [instrument][] to achieve the same goal". That does leave quite a lot of fluffyness around the goal (which should normally be unambiguosly defined), but that is maybe OK for an Assumption?
 
 ## Assumptions
@@ -65,7 +65,7 @@ For each test target, at least one of the following is true:
 
 #### Passed Example 1
 
-This ...
+This `link` has a [clickable area][] of 44×? pixels.
 
 ```html
 <style>

pages/glossary/can-be-targeted-by-pointer-event.md

@@ -11,7 +11,9 @@ input_aspects:
 An element _can be targeted by pointer events_ when both the following conditions are true:
 
 - the element is [focusable][]; and
-- the element is [visible][]. <- not covered, even by transparent stuff…
+- the element is not totally [obscured][]. <- not covered, even by transparent stuff…
+
+> **Comment:** if a transparent element completely covers it (and intercept clicks), then the element cannot be clicked.
 
 [focusable]: #focusable 'Definition of Focusable'
 [visible]: #visible ' Definition of Visible'