Two ways forward here:

1. Be explicit each time and use "DOM attribute" or "IDL attribute" everywhere.
2. Use "attribute" to mean "DOM attribute" and JS-centric terms ("property" or "accessor" depending on the case) to refer to IDL attributes ( basically what Make 6.1 more inclusive of non-Web JS APIs #435 was trying to do)

@hober has expressed a strong preference for 1 and strong opposition to 2, so it may be the path of least resistance to just go with 1 which at least resolves the inconsistency.

I think I agree with a preference for 1. If you look for example at all of the text in https://w3ctag.github.io/design-principles/#attributes-vs-methods - it really seems clearer.

Discussed in breakout and agreed to use option 1. @hober to write a PR.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Working_with_Objects uses the word "property". I understand that IDL uses "attribute", but we aren't really talking about IDL as much as we are talking about the objects that are described using IDL.

"Use attributes or methods appropriately" -> "Properties and getters should behave like properties not methods".